| Notice |
| Document Life Cycle
| Document Historv |
|
| Acknow vii
| Some of the Operators interviewed |
| Contributors |
|
| References |
| Table of Contents |
| Table of Fi xv |
| Preface
|
| Chapter 1 – Document Objectives
| Objectives of this document
| Define Common Terminology |
| Consensus Tool |
| Using This Document |
|
| Intended Audience |
| Relationship to Standardization
Activities |
| Terms and Definitions
| Customer |
| Service Provid |
| Network Oper |
| Supplier |
| End-to-End Process Flow |
|
|
| Chapter 2 – The TMN Model |
| Chapter 3 – Business Drivers
| The Business Challenge
| The Importance of Service |
| Linking Objectives and
Requirements |
| Business Process Models |
|
|
| Chapter 4 - Business Relationship
Reference Model and Telecom Operations Map
| Business Relationship Reference
Model
| Standardizing Process
Interfaces |
| Management Value Chain |
| Supplier Int |
| Network Management
Relationships |
|
| Telecom Operations Map Overview |
|
| Chapter 5 -
Процессы и функции управления сетью
|
| Chapter 6 – Deploying Network
Management Solutions
| Technical Boundaries |
| Relationship with the Telecom
Operations Map |
| Factors for Distribution of
Functionality |
| Key Criteria for Partitioning
Functionality |
|
| Chapter 7 - Evaluation of Process
Automation Needs
| Network Development Process |
| Network Planning Process |
| Network Provisioning Process |
| Network Inventory Management
Process |
| Network Maintenance and
Restoration Process |
| Network Data Management Process |
|
| Chapter 8 – Glossary of Terms and
Acronyms |
| ANNEX A: TMN and Role of Network
Management |
| ANNEX B: Service Related Lifecycles
| The Customer Care Lifecycle |
| The Service Management Lifecycle |
| The Network Management Lifecycle
| Lifecycle In |
|
|
| ANNEX C: M.3400 Functions
Applicable to the NM Detailed Operations Map |
| ANNEX D: Expansion of High Level
Business Processes
| Business Process Mapping Examples
| Network Provisioning Process
Example |
| Network Data Management
Process Example |
|
| Detailed Descriptions of
Sub-Processes
| Performance Monitoring and
Analysis Sub-process |
| Network Test Management
Sub-process |
| Network Configuration &
Routing Sub-process |
|
|
| Appendix
| Partitioning of Function Set
Groups (M3400) and Data Areas into Generic and Sub-Network
Function |
| Set Groups, Data Areas and Generic
Sub-Network Interfaces |
| Introduction |
| Partitioning of Function Set
Groups |
| Partitioning of Data Areas |
| NM Function Set Groups and Data
Areas (Generic)
| Function Groups (Generic) |
| Data Areas (Generic) |
|
| Sub-Network (Technology Related)
Function Set Groups, Data Areas, and Interfaces
| Sub-Network Function Set
Groups |
| Sub-Network Data Areas |
| Sub-Network Generic Interfaces |
|
|
TM
Forum Approach Defined
The TM Forum approach is a holistic, business-driven approach to
achieving OSS integration by building on the TMN model (the
Telecommunications Management Network model produced by ITU-T). The goal
of TM Forum is to make it possible for service providers and operators
to provide services efficiently, using Commercial Off-the-Shelf (COTS)
software as much as possible – to become ‘ Smooth Operators’ in
the best sense of the word.
To that end, TM Forum provides investment direction as well as
development specifications needed to produce management systems. It
addresses the problem of business process automation and OSS integration
in a holistic and pragmatic way. Specifically, TM Forum brings three
essential elements to bear on the TMN layered model:
A business process-driven approach. The TM Forum approach starts from
the premise that Service Provider and Network Operators need to automate
their business processes, which means information needs to flow from
end-to-end across many different systems. Only when a process is
understood and the linkages are clear is it possible to apply standards
in a way that delivers business value.
Technology-independent agreements. Business agreements about what
information will flow between and within processes must be kept
independent of the protocols used to implement those agreements. The
approach documents all agreements in technology-neutral form, so that
the same agreement can be implemented in multiple technologies as they
continue to evolve.
Products, not just paper. A main premise of is that paper standards
are not sufficient to solve business problems. Products, not paper, are
the end goal, provided documentation is produced to support the
replications of industry agreements across multiple vendors' products.
Components
of the TM Forum Approach
In order to address all three of these
principles, the TM Forum approach consists of multiple components as
shown in Figure P.1
High-level direction – a sense of ‘
which way is west’ to enable service providers and suppliers to make
basic investment decisions about their business processes and technology
choices. This direction takes the form of the Telecom Operations Map and
companion documents, like the Network Management Detailed Operations Map,
as well as the Technology Integration Map.
Specific agreements – precise
requirements and the specifications of what information is to be
exchanged between any two processes or systems, provided in
technology-neutral form and accessible through the Central Information
Facility. In addition, specifications for technology integration points
are provided.
Catalyst projects –
an environment in which to promote the integration of existing products,
and to gain development experience to test the precepts of the ‘ Maps’
and the viability of specific information agreements.
Рис.
Р.1. Подход форума к интеграции Системы
поддержки операций (СПО)
(Operation Support System - OSS)